Skip to content
This repository was archived by the owner on May 28, 2021. It is now read-only.

Keep mysql readonly after exit group unintentionally #261

Conversation

alantang888
Copy link

@alantang888 alantang888 commented Mar 19, 2019

Since MySQL version >= 8.0.12, <= 8.0.15 changed group-replication-exit-state-action default behavior to ABORT_SERVER. Which will shutdown the server after exit group unintentionally. It should better change server to READ_ONLY instead of exit.

Future version MySQL also change this behavior back to READ_ONLY
https://dev.mysql.com/doc/refman/8.0/en/group-replication-options.html#sysvar_group_replication_exit_state_action

Signed-off-by: Alan Tang alantang888@gmail.com

@alantang888 alantang888 changed the title Keep mysql readonly after exit group unintentionally Keep mysql readonly after exit group unintentionally exit Mar 19, 2019
@alantang888 alantang888 changed the title Keep mysql readonly after exit group unintentionally exit Keep mysql readonly after exit group unintentionally Mar 19, 2019
@alantang888
Copy link
Author

Oh! the signed-off used another email address. Should I need to modify it?

Since mysql version >= 8.0.12, <= 8.0.15 changed default behavior
to `ABORT_SERVER`. Which will shutdown the server after exit group
unintentionally. It should better change server to `READ_ONLY` instead
of exit.

Future version MySQL also change this behavior back to `READ_ONLY`
https://dev.mysql.com/doc/refman/8.0/en/group-replication-options.html#sysvar_group_replication_exit_state_action

Signed-off-by: Alan Tang <alantang888@gmail.com>
@prydie
Copy link

prydie commented Mar 19, 2019

If you wouldn't mind, thanks!

@alantang888 alantang888 force-pushed the set_group-replication-exit-state-action_to_readonly branch from 8bd10fe to 293bad9 Compare March 19, 2019 10:00
@alantang888
Copy link
Author

Ok, modified. Thanks a lot.

@prydie
Copy link

prydie commented Mar 19, 2019

E2E tests seem to be failing with:

9-03-19T10:15:42.697657Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2019-03-19T10:15:42.697851Z 0 [ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-001146 - Table 'mysql.component' doesn't exist
2019-03-19T10:15:42.697888Z 0 [Warning] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-003543 - The mysql.component table is missing or has an incorrect definition.
2019-03-19T10:15:42.697999Z 0 [ERROR] [MY-011071] [Server] unknown variable 'group-replication-exit-state-action=READ_ONLY'
2019-03-19T10:15:42.698022Z 0 [Warning] [MY-010952] [Server] The privilege system failed to initialize correctly. If you have upgraded your server, make sure you're executing mysql_upgrade to correct the issue.
2019-03-19T10:15:42.698113Z 0 [ERROR] [MY-010119] [Server] Aborting

@alantang888
Copy link
Author

oh... upgrade test. I need to take care of version before 8.0.12...

Signed-off-by: Alan Tang <alantang888@gmail.com>
@alantang888 alantang888 force-pushed the set_group-replication-exit-state-action_to_readonly branch from 0b8208e to 7377f35 Compare March 20, 2019 03:31
Not realized there already have semver can use before.

Signed-off-by: Alan Tang <alantang888@gmail.com>
@alantang888 alantang888 force-pushed the set_group-replication-exit-state-action_to_readonly branch from 7377f35 to 9d02772 Compare March 20, 2019 03:39
@alantang888
Copy link
Author

Sorry, I think i didn't test it well before PR...

Because MySQL check variable before load group replication plugin

Signed-off-by: Alan Tang <alantang888@gmail.com>
@alantang888
Copy link
Author

This time I don't know why the upgrade test is failed...

@prydie prydie merged commit cfc3e5b into oracle:master Mar 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants